Skip to content

Conversation

@wmedvede
Copy link
Contributor

@wmedvede wmedvede commented Jun 11, 2025

Closes: #1182
Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to our code style
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
  • Pull Request contains link to the issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-quarkus2 to backport the original PR to the quarkus2 branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

…ception when adding the token to the request header parameters
@wmedvede wmedvede requested a review from a team as a code owner June 11, 2025 11:49
Copy link
Member

@ricardozanini ricardozanini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a DEBUG log when the token is not found?

@wmedvede
Copy link
Contributor Author

@ricardozanini your suggestions has been added.

@ricardozanini ricardozanini merged commit c6e504a into quarkiverse:main-lts Jun 11, 2025
11 checks passed
wmedvede added a commit to wmedvede/quarkus-openapi-generator that referenced this pull request Jun 12, 2025
…ception when adding the token to the request header parameters (quarkiverse#1184)

* issue-1182: Token propagation throws java.lang.UnsupportedOperationException when adding the token to the request header parameters

* Review comments 1

* Review comments 2

(cherry picked from commit c6e504a)
ricardozanini pushed a commit that referenced this pull request Jun 12, 2025
…ception when adding the token to the request header parameters (#1184) (#1189)

* issue-1182: Token propagation throws java.lang.UnsupportedOperationException when adding the token to the request header parameters

* Review comments 1

* Review comments 2

(cherry picked from commit c6e504a)
ricardozanini pushed a commit to ricardozanini/quarkus-openapi-generator that referenced this pull request Jun 18, 2025
…ception when adding the token to the request header parameters (quarkiverse#1184) (quarkiverse#1189)

* issue-1182: Token propagation throws java.lang.UnsupportedOperationException when adding the token to the request header parameters

* Review comments 1

* Review comments 2

(cherry picked from commit c6e504a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Token propagation throws java.lang.UnsupportedOperationException when adding the token to the request header parameters

4 participants